Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
Perfetto is super useful for understanding interactions between the kernel and applications. Outside of Android and ChromeOS, though it's use isn't as common. This doc tries to provide a basic walk through to get started using perfetto for upstream kernel development with classic linux distros, potentially running under qemu.
Grab the latest linux- tarball: https://github.com/google/perfetto/releases
Often the tests I’m tracing need to run as root, so because of this, I copied the
binaries in the tarball to /usr/local/bin/ and chmod +x the binaries to make
Add Graal JIT Compilation to Your JVM Language in 5 Steps, A Tutorial http://stefan-marr.de/2015/11/add-graal-jit-compilation-to-your-jvm-language-in-5-easy-steps-step-1/
The SimpleLanguage, an example of using Truffle with great JavaDocs. It is the officle getting-started project: https://github.com/graalvm/simplelanguage
Truffle Tutorial, Christan Wimmer, PLDI 2016, 3h recording https://youtu.be/FJY96_6Y3a4 Slides
| import 'package:flutter/material.dart'; | |
| /// `ThemeExtension` template for custom colors. | |
| /// | |
| /// For example purposes, it has all required fields from the default Material `ColorScheme`. | |
| /// But you can add, rename and delete any fields your need. | |
| /// | |
| /// ### Motivation | |
| /// | |
| /// At the beginning, you may not know if your colors will fit into the Material `ColorScheme`, |
| [ | |
| { | |
| "bindings": { | |
| // Built-in | |
| "ctrl-g": "menu::Cancel", | |
| "ctrl-x 5 2": "workspace::NewWindow", | |
| "ctrl-x ctrl-c": "zed::Quit", | |
| "ctrl-x ctrl-f": "workspace::Open", | |
| "ctrl-x k": "pane::CloseActiveItem", | |
| "ctrl-x o": "workspace::ActivateNextPane", |
| #! /usr/bin/bash | |
| read -p "Give size of swap you wants to create:" usr_input | |
| echo "Your swap memory will be create of size : $usr_input" | |
| sudo fallocate -l $usr_input /swapfile | |
| sudo chmod 600 /swapfile | |
| sudo mkswap /swapfile | |
| sudo swapon /swapfile | |
| sudo swapon --show |
In multiplayer game, one of the most complex issue is to keep all player's state in sync with server state. There are a few good articles around this topic on the internet. However, some details are missing here and there, which may be confusing for beginners in field of game programming, I hope I can clear things up in this article.
I'll present a few techniques commonly used in this problem space.
Before we jump into the problem, let's have an overview on how multiplayer game generally works.
Typically, a game program needs to simulate
| /interface wireless channels | |
| add band=2ghz-b/g/n width=20 list=2GHz/20MHz frequency=2412 name=ch1 | |
| add band=2ghz-b/g/n width=20 list=2GHz/20MHz frequency=2437 name=ch6 | |
| add band=2ghz-b/g/n width=20 list=2GHz/20MHz frequency=2462 name=ch11 | |
| add band=5ghz-onlyac width=20 list=5GHz/80MHz extension-channel=Ceee frequency=5180 name=ch36/38/42 | |
| add band=5ghz-onlyac width=20 list=5GHz/80MHz extension-channel=eCee frequency=5200 name=ch40/38/42 | |
| add band=5ghz-onlyac width=20 list=5GHz/80MHz extension-channel=eeCe frequency=5220 name=ch44/46/42 | |
| add band=5ghz-onlyac width=20 list=5GHz/80MHz extension-channel=eeeC frequency=5240 name=ch48/46/42 |
| from rdp import rdp | |
| def angle(directions): | |
| """Return the angle between vectors | |
| """ | |
| vec2 = directions[1:] | |
| vec1 = directions[:-1] | |
| norm1 = np.sqrt((vec1 ** 2).sum(axis=1)) | |
| norm2 = np.sqrt((vec2 ** 2).sum(axis=1)) |
